This PR adds a Github action workflow that responds to merged pull requests which impact /registry resources.

The action is implemented in /automation/publish.go and performs the following steps for each added or modified connector:

• Download tgz
• Re-upload tgz to a stable location [requires bucket key]
• Extract contents
• Build payload for API
• Upsert to API (gql/RESTified) [requires Hasura key] ( https://data.pro.arusah.com/console/ )

This should ensure that the registry DB is up to date with the latest changes to the /registry directory in this repository.

Roadmap

These changes are step 1 in a distribution automation roadmap as described in /rfcs/0002-distribution-gh.md which has also been updated to reflect the most recent version of this plan.

At a high-level, the roadmap steps are:

1. Add a Github action to update the registry DB when PRs to this repo modifying /registry files are altered
2. Turn the majority of the previous action into an infra-as-code service in v3-connector-platorm.
3. Design and deploy auth solution for this service that has roles restricting access to owned connectors
4. Create a public GH action to use this service to allow self-service publication of connectors
5. Party